Switchbot Cloud: Fixed binary sensors didn't update automatically#158434
Conversation
|
Hey there @SeraphicRav, @laurence-presland, @Gigatrappeur, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
|
Hi Xiaoling-git! This PR looks like it should fix the related issue. But the title is misleading and the description could be more complete.
|
|
I'm very sorry for confusioning you. I work at Switchbot and have recently received a lot of customer feedback about binary sensors not automatically updating their status. After carefully reviewing the code, I made some modifications that I hope will help. I've already tested the functionality on a contact sensor, and it works. |
|
Great! Thanks for the clarification. I was able to get the context of the bug by looking at the conversation in the linked issue. What I mean is: in order for someone to review this, there needs to be a way to verify that this change is working and doesn't break anything. At first glance, it looks like a small, harmless change. But if you could add a specific test to assert the fix, that would be great. If—because of the nature of this change—this isn't something that can be easily tested, please mention the existing test that covers this part, or (not ideal) describe in detail the local testing you did with the sensor. |
…58434) Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
Breaking change
Proposed change
Make sure update state once every 10 min
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: